Methods of operating memory devices and electronic systems having memory devices

ABSTRACT

Methods of operating memory devices and electronic systems having memory devices include initiating a boot mode of operation of the memory device in response to receiving a first command, wherein the first command comprises a pattern of two or more command signals, and terminating the boot mode of operation in response to receiving a second command, wherein the second command comprises a pattern of two or more command signals.

RELATED APPLICATIONS

This Application is a Continuation of U.S. application Ser. No.12/116,325, titled “MEMORY DEVICE INITIATE AND TERMINATE BOOT COMMANDS”filed May 7, 2008, (allowed) which is commonly assigned and incorporatedherein by reference.

TECHNICAL FIELD

The present disclosure relates generally to memory devices and inparticular the present disclosure relates to methods and apparatus foraccessing boot data stored in a memory device.

BACKGROUND

Memory devices are typically provided as internal, semiconductor,integrated circuits in computers or other electronic devices. There aremany different types of memory including random-access memory (RAM),read only memory (ROM), dynamic random access memory (DRAM), synchronousdynamic random access memory (SDRAM), and flash memory.

Flash memory devices have developed into a popular source ofnon-volatile memory for a wide range of electronic applications.Non-volatile memory is memory that can retain its stored data for someextended period without the application of power. Common uses for flashmemory and other non-volatile memory include personal computers,personal digital assistants (PDAs), digital cameras, digital mediaplayers, digital recorders, games, appliances, vehicles, wirelessdevices, mobile telephones and removable memory modules, and the usesfor non-volatile memory continue to expand.

Flash memory devices typically use a one-transistor memory cell thatallows for high memory densities, high reliability, and low powerconsumption. Storing data in a flash memory cell can be accomplished bychanging the threshold voltage of the cell, through programming or“writing” of charge storage nodes, such as floating gates or trappinglayers or other physical phenomena. By defining two or more ranges ofthreshold voltages to correspond to individual data states, one or morebits of information may be stored on each cell. Examples are singlelevel and multilevel memory cells.

Flash memory typically utilizes one of two basic architectures known asNOR flash and NAND flash. The designation is derived from the logic usedto read the devices. In NOR flash architecture, a column of memory cellsare coupled in parallel with each memory cell coupled to a transferline, often referred to as a bit line. In NAND flash architecture, acolumn (e.g., NAND string) of memory cells are coupled in series withonly the first memory cell of the column coupled to a bit line.

In many modern flash memory device implementations, the host interfaceand erase block management routines additionally allow for the flashmemory device to appear as a read/write mass storage device (e.g., amagnetic disk) to the host. One such approach is to conform theinterface to the flash memory to a standard interface for a conventionalmagnetic hard disk drive allowing the flash memory device to appear as ablock read/write mass storage device or disk. This approach has beencodified by the Personal Computer Memory Card International Association(PCMCIA), Compact Flash (CF) and Multimedia Card (MMC) standardizationcommittees, which have each promulgated a standard for supporting flashmemory systems, which are sometimes referred to as flash memory “cards”,which can emulate a hard disk drive protocol. Other such protocols existas are known to those skilled in that art.

A typical operation performed by a host (e.g., processor) is to bootload upon power-up or a reset of the host system. This boot operationtypically involves loading boot (e.g., system initialization) data froma memory device coupled to the host. In some systems, this operation isset in motion by applying a continuous clock signal and driving an inputof a memory device storing the boot data to a fixed state (e.g., logiclevel 0 or 1) for a particular number of clock cycles. In such a system,the signal being driven to the fixed state for the required amount oftime along with the applied clock signal are interpreted by the memorydevice as an indication to output boot data. One issue that can resultfrom this method is that noise may appear on the signal and might beinterpreted as an indication to terminate the boot operation when it wasnot intended. This would result in a failed boot load attempt. Anotherissue is that some hosts may not be configured to drive the signal to afixed state for the required amount of time. Thus, some memory devicesmay require a hardware change to be able to utilize the boot methoddescribed above.

Thus, for the reasons stated above, and for other reasons that willbecome apparent to those skilled in the art upon reading andunderstanding the present specification, there is a need in the art foradditional and more robust methods of performing boot operations with ahost coupled to one or more memory devices.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram of an electronic system having atleast one memory device according to an embodiment of the presentdisclosure.

FIG. 2 is a functional block diagram of an electronic system having atleast one MMC memory device according to an embodiment of the presentdisclosure.

FIG. 3 is a timing diagram illustrating an initiation of a bootoperation according to an embodiment of the disclosure.

FIG. 4 is a timing diagram illustrating a termination of a bootoperation according to an embodiment of the disclosure.

DETAILED DESCRIPTION

In the following detailed description of the present embodiments,reference is made to the accompanying drawings that form a part hereof,and in which is shown by way of illustration specific embodiments inwhich the disclosure may be practiced. These embodiments are describedin sufficient detail to enable those skilled in the art to practice theembodiments of the invention, and it is to be understood that otherembodiments may be utilized and that electrical, mechanical or processchanges may be made without departing from the present disclosure. Thefollowing detailed description is, therefore, not to be taken in alimiting sense.

FIG. 1 is a functional block diagram of an electronic system accordingto one or more embodiments of the present disclosure. The memory device100 is coupled to a processor 110. The processor 110 can be amicroprocessor or some other type of controlling circuitry. The memorydevice 100 and the processor 110 form part of the electronic system 120.The memory device 100 has been simplified to focus on features of thememory that are helpful in understanding the embodiments of the presentdisclosure.

The memory device 100 includes an array of memory cells 130 that can bearranged in banks of rows and columns. For example, the memory array canbe an array of flash memory cells arranged in a NAND or NORconfiguration.

Row decode circuitry 144 and column decode circuitry 150 are provided todecode address signals. Address signals are received and decoded toaccess memory array 130. Memory device 100 also includes input/output(I/O) control circuitry 160 to manage input of commands, addresses anddata to the memory device 100 as well as output of data and statusinformation from the memory device 100. An address register 140 iscoupled between I/O control circuitry 160, row decode circuitry 144 andcolumn decode circuitry 150 to latch the address signals prior todecoding. A command register 148 is coupled between I/O controlcircuitry 160 and control logic 170 to latch incoming commands. Controllogic 170 controls access to the memory array 130 in response to thecommands and generates status information for the external processor110. The control logic 170 is coupled to row decode circuitry 144 andcolumn decode circuitry 150 to control the row decode circuitry 144 andcolumn decode circuitry 150 in response to the addresses. Control logic170 also comprises in part, various structures and circuits in order tofacilitate implementation of the various embodiments of the presentdisclosure. For example, control logic 170 can include a state machineand/or various logic circuits and control registers. The memory device100 is configured to initiate a boot operating mode in accordance withone or more embodiments of the disclosure.

Control logic 170 is also coupled to a cache register 152. Cacheregister 152 latches data, either incoming or outgoing, as directed bycontrol logic 170 to temporarily store data while the memory array 130is busy writing or reading, respectively, other data. During a writeoperation, data is passed from the cache register 152 to data register146 for transfer to the memory array 130; then new data is latched inthe cache register 152 from the I/O control circuitry 160. During a readoperation, data is passed from the cache register 152 to the I/O controlcircuitry 160 for output to the external processor 110; then new data ispassed from the data register 146 to the cache register 152. A statusregister 156 is coupled between I/O control circuitry 160 and controllogic 170 to latch the status information for output to the processor110.

Memory device 100 receives control signals at control logic 170 fromprocessor 110 over a control link 172. The control signals present onthe control link 172 may include a chip enable CE#, a command latchenable CLE, an address latch enable ALE, a write enable WE#, a readenable RE# and a write protect WP# signal. Memory device 100 receivescommands (in the form of command signals), addresses (in the form ofaddress signals), and data (in the form of data signals) from processor110 over a multiplexed input/output (I/O) bus 162 and outputs data toprocessor 110 over I/O bus 162.

Specifically, the commands are received over input/output (I/O) pins[7:0] of I/O bus 162 at I/O control circuitry 160 and are written intocommand register 148. The addresses are received over input/output (I/O)pins [7:0] of bus 162 at I/O control circuitry 160 and are written intoaddress register 140. The data are received over input/output (I/O) pins[7:0] for an 8-bit device or input/output (I/O) pins [15:0] for a 16-bitdevice at I/O control circuitry 160 and are written into cache register152. The data are subsequently written into data register 146 forprogramming memory array 130. For another embodiment, cache register 152may be omitted, and the data are written directly into data register146. Data are also output over input/output (I/O) pins [7:0] for an8-bit device or input/output (I/O) pins [15:0] for a 16-bit device. Itwill be appreciated by those skilled in the art that additionalcircuitry and signals (e.g., system clock) can be provided, and that thememory device of FIG. 1 has been simplified to help focus on the presentdisclosure. Additionally, while the memory device of FIG. 1 has beendescribed in accordance with popular conventions for receipt and outputof the various signals, it is noted that the various embodiments are notlimited by the specific signals and I/O configurations described unlessexpressly noted herein.

One such type of memory device 100 is an MMC type memory device. FIG. 2illustrates a system according to an embodiment of the presentdisclosure utilizing an MMC memory device. As with the systemillustrated in FIG. 1, FIG. 2 has been simplified to focus on featuresof the system that are helpful in understanding the present disclosure.Other circuitry and functionality including that illustrated in FIG. 1can be present in the system shown in FIG. 2 as is known to thoseskilled in the art. The system 220 shown in FIG. 2 comprises a host 210and an MMC memory device 200. For example, the host 210 may be aprocessor or other type of controller external to the MMC memory device200. The clock (CLK) signal 224 may be generated by the host 210 asshown or may be generated by some other clock source separate from thehost 210. MMC commands are transferred between the host 210 and the MMCmemory device by a serial bidirectional command (CMD) signal 226. Datais transferred between the host 210 and memory device 200 by abidirectional data bus 222. Although data bus 222 is shown in FIG. 2 asan 8-bit (DAT [7:0]) data bus, other data bus widths are possibleaccording to various embodiments of the present disclosure. Powerconnections for VDD 228 and VSS 230 are also shown. The memory device200 is not limited to the signals illustrated in FIG. 2. For example,additional power/ground and communication signals may be present betweenthe memory device 200 and the host 210. Control circuitry 232 serves tocontrol the operation of the memory device according to the embodimentsof the present disclosure and is illustrated in a simplified form. Thecontrol circuitry can include a state machine and/or various logiccircuits and control registers. These control registers can compriseconfiguration registers storing bits which indicate a number of possibleconfigurations for the memory device. Control circuitry 232 can alsoinclude one or more of the functional blocks (e.g., 140, 144, 146, 148,150, 152, 156, 160, 170) illustrated in FIG. 1. Additional analog and/ordigital circuitry to facilitate implementation of the variousembodiments of the present disclosure can also be included in controlcircuitry 232.

MMC memory devices can be Read Only devices or can also be Read/Writedevices. Read Only devices are pre-programmed, typically by a vendor ormanufacturer and generally cannot be written to in routine operation.Read/Write devices may be written to one or more times. For example,memory array 234 can be an array of flash memory cells which can beprogrammed many times. MMC memory devices 200 may also contain one timeprogrammable memory that allows the memory to be programmed one time bya user.

FIG. 3 illustrates signal waveforms for a boot operation according toone or more embodiments of the present disclosure such as the system 220shown in FIG. 2. The uppermost waveform 302 of FIG. 3 represents theapplication of power to a memory device such as memory device 200.Waveform 302 can be representative of VDD 228 and the dotted line 303can be representative of VSS 230. For example, VDD can be 2.7 to 3.6 Vwherein VSS is substantially equal to a ground potential. However, theembodiments are not limited to these power supply levels as other powersupply potentials are known to those skilled in the art.

Waveform 304 represents a clock (CLK) signal 224 (e.g., system clock)supplied to the memory device 200. This clock signal 304 can begenerated by a host 210 or may be supplied to the memory device 200 andhost 210 by an external clock source (not shown.) According to theembodiment of FIGS. 2 and 3, the clock 224/304 may have a frequency inthe range of 0 to 52 MHz. However, the embodiments of the presentinvention are not limited to a specific fixed or range of clockfrequencies. Commands present on the command (CMD) signal line 306 anddata presented on the data lines (DAT[7:0]) 308-312 are synchronizedwith clock signal 304/224.

The command signal 306 is transferred via a bidirectional command line.MMC commands 316 appearing on the command signal line 226/306 arecomprised of 48 bits and are each preceded by a start bit 314 andsucceeded by an end bit 318. For example, in the embodiments representedby FIGS. 3 and 2, start bits 314 have a logical 0 value wherein end bits318 have a logical 1 value. Table 1 provides the format for an MMCcommand. As the command signal 306 is bidirectional, one of the host 210or the memory device 200 can act as a driver while the other acts as areceiver. A multitude of commands adhering to the format shown in Table1 are possible according to a standard MMC protocol with regard to oneor more of the embodiments of the present disclosure. Other commands arepossible as are known in the art. A command in the MMC protocoltypically is denoted as a “CMDX” command where ‘X’ is a number whichidentifies the actual command. For example, an MMC CMD0 refers to a“GO_IDLE_STATE” which acts as a reset signal for the memory device. Forsuch an embodiment, the desired command is designated by the command(which are sometimes referred to as base bits), e.g., bits 45:40, andthe command (sometimes referred to as a base command) may be accompaniedby an argument, e.g., bits 39:8, further defining the action of thedesignated command. In existing MMC devices, the argument (e.g., asshown in Table 1) of a CMD0 command are stuff bits as there is nofurther definition required by the memory device receiving this command.Another example of an MMC command is a CMD17 (“READ_SINGLE_BLOCK”)command wherein the argument comprises the address of the block of datato be read from the memory device 200. Other commands exist in the MMCprotocol as are known to those skilled in the art.

TABLE 1 MMC Command Format Start Command Argu- End Description BitTransmission Bit (Base) ment CRC Bit Bit Position 47 46 [45:40] [39:8][7:1] 0 [47:0] Logical  0 1 = Host X X X 1 Value 0 = Memory Device Note:X = Logical 1 or 0 CRC = Cyclic Redundancy Check

A boot operation in MMC devices can be initiated by the host 210 drivingthe command line 226 to a low, or logical 0, state for at least 74 clockcycles following power-up of the memory device 200. If intentional orunintentional activity (e.g., noise) occurs on the command line 226following power-up, other than continuously holding the line low for 74clock cycles, the memory device 200 is locked out of initiating (e.g.,entering) a boot mode until power is cycled on the memory device 200.Termination of the boot operation occurs when the command line is drivento a high (e.g., logical 1) state. Thus, any noise appearing on thecommand line 226 during a boot operation could be perceived by thememory device 200 as an indication to prematurely terminate the bootoperation. This would result in a failed boot load attempt. This MMCboot initiation/termination method may cause issues with some hostswhich were not originally designed to accommodate the MMC boot modedescribed above. For example, some hosts utilize hardware to generatecommands which strictly adhere to the command structure shown inTable 1. In such devices, a hardware modification would be required forthese hosts to utilize the MMC boot method of driving the CMD signal 226low for a minimum of 74 clock cycles to initiate a boot mode ofoperation and further to maintain the low state of the CMD signal 226throughout the boot operation.

A boot mode of operation in the MMC memory device is different thanperforming a typical read operation of the memory device. In the MMCexample, a read operation involves reading the contents of the memorydevice from a user (e.g., host) specified address. Before a readoperation can occur the MMC device must be transitioned from anidentification mode to a transfer mode through a series of handshakingcommand and response sequences, typically a minimum of 5 steps, but canbe more if the device is to be operated with a bus width greater than1-bit. The boot mode of operation causes the output of boot data tooccur without the need for the handshaking sequences and addresstransfers required of a read operation.

A boot operation according to one or more embodiments of the presentdisclosure is described by way of reference to the timing diagramsillustrated in FIGS. 3 and 4 and the system shown in FIG. 2. A bootoperation according to one or more embodiments of the presentdisclosure, with reference to an MMC memory device 200 as shown in FIG.2, should be initiated after the power supply for the memory device hasbecome stable. The power supply can be presumed stable after aparticular number of clock pulses 330 have occurred since power-up orreset. In the case of an MMC memory device, this number of clock pulses330 can be 74. Other memory devices may have a different number of clockpulses occurring prior to allowing the initiation of a boot operationaccording to the one or more embodiments of the present disclosure.

A boot operation can be initiated according to one or more embodimentsof the present disclosure by the host 210 sending a particular command(e.g., base command or base command plus argument) to initiate a bootoperation. As one example, in the case of an MMC memory device, theinitiate boot command may be a CMD0 command having a unique argument314-318 indicative of a desire to initiate the boot operating mode. Theformat of the initiate boot command (e.g., CMD0 with unique argument)under this protocol would adhere to the format shown in Table 1 above.The unique argument may comprise any unique value so long as the memorydevice recognizes that the CMD0 having the unique argument comprises aninitiate boot command and not a generic CMD0 (e.g., simple reset)command. For example, the unique argument can consist of a hexadecimalvalue of 0×FFFFFFFA. The initiate boot command can also comprise CRCdata while adhering to the format shown in Table 1. In general, thememory device is configured to recognize a pattern of two or morecommand signals as indicative of a desire to initiate a boot operatingmode, and to initiate the boot operating mode in response to thatpattern of two or more command signals.

Upon receipt of the initiate boot command 316 and end bit 318, thememory device 200 initiates a boot mode of operation if the memorydevice has been enabled as a boot enabled device. For example, multiplememory devices may be coupled to the command and data bus as shown inFIG. 2. Thus, a selected memory device can be boot enabled so only thatdevice responds to an initiate boot command provided by the host 210.The boot enabled memory device may be configured to respond to areceived initiate boot command with a boot acknowledge responsepresented on the DAT[0] signal as indicated by the dashed lines of 320.This can be desirable in systems utilizing multiple memory deviceswherein the host may be ‘polling’ the multiple memory devices todetermine which memory device responds to indicate that it is the bootenabled memory device. A system having a single memory device may or maynot be configured to respond with a boot acknowledge response 320.According to one embodiment, the format of the boot acknowledge responsemay be a start (e.g., 0) bit followed by a ‘010’ bit pattern followed byan end (e.g., 1) bit. For example, the boot acknowledge response 320generated by the memory device 200 and presented on the DAT[0] signalline 308 can be a bit pattern of 00101. Other boot acknowledge bitpatterns 320 are possible according to the various embodiments of thepresent disclosure. If configured to do so, the memory device may berequired to output the boot acknowledge response 320 within a particulartime frame following the receipt of an initiate boot command, as definedby the protocol under which the memory device is operating. For example,an MMC memory device configured to output a boot acknowledge responsemust output the boot acknowledge response within a time-out ‘TO1’ timeof 50 ms 332 of receipt of the initiate boot command to avoid a time outcondition. However, the many embodiments are not limited to the 50 msresponse time. If the memory device is not configured to output a bootacknowledge response, a different time out condition may also occur ifthe beginning of the boot data 322 is not presented on the data line 308by a different time-out time ‘TO2’ 334.

Following the output of a boot acknowledge response 320, if configuredto do so, the memory device 200 then begins to output boot data 322-324from the boot data locations of the memory device. The memory device maybe configured to utilize one or more boot partitions of the memorydevice. For example, an MMC memory device may have two boot partitionsavailable to boot from. The memory device 200 may also access the userarea of the memory device to boot from. The area containing the bootdata is designated in the memory device, i.e., the memory device isconfigured to define where it will look for boot data when the boot modeof operation is initiated. Thus, to initiate the boot mode of operation,no address need be provided to the memory device because the memorydevice controls where it will access the boot data. In the MMC memorydevice example, a minimum boot partition size may be 128KB wherein themaximum boot partition size is determined by a boot partition sizemultiplier such that the actual boot partition size is equal to128KB*BOOT_PARTITION_MULTIPLIER. The boot partition multiplier value mayhave been stored previously in the memory device 200. The output of bootdata is synchronized with the system clock 304 and continues until alldata of the designated area has been outputted or the boot mode ofoperation has been terminated. The format of the boot data322-328,420-428 may be that of a start bit (e.g., 0) followed by aportion of boot data followed by an end (e.g., 1) bit as shown in FIGS.3 and 4. If configured, the MMC memory device may also present boot dataon data lines in addition to the DAT[0] line 308 such as theDAT[0]−DAT[n] data lines 310-312. For an MMC memory device, n may be anynumber up to 7 under current standards. Other memory devices accordingto the various embodiments are not so limited to 8 (e.g., DAT[0]-DAT[7])data lines.

Termination of the boot load operation (e.g., the memory device exitingboot mode) according to embodiments of the present disclosure can occurwhen a valid terminate boot CMD0 command 414-418 is transmitted on theCMD bus 226 by the host 210. According to the MMC protocol, the bootoperation will also be terminated if all of the contents of the enabledboot partition(s) have been sent to the host. However, in one or moreembodiments, the boot operation can only be terminated prior tooutputting the entire contents of the enabled boot partition(s) if avalid terminate boot command is received by the memory device. Aterminate boot command may also adhere to the format as shown inTable 1. For example, the terminate boot command could also conform tothe CMD0 command protocol. The argument of the terminate CMD0 command414-418 can have any value as long as it differs from the uniqueargument used in conjunction with the initial CMD0 command 316transmitted by the host 210 to initiate the boot operation. The host maysend the terminate boot CMD0 command 416 while data 420-424 is stillbeing output on the data bus lines 308-312. Output of data will cease inresponse to receipt 430 by the memory device 200 of the end bit 418 ofthe terminate boot command 416. Data 424-428 on the data lines 308-312may or may not coincide precisely with the termination of the bootoperation 430. In an alternative embodiment indicated by the dashedlines surrounding command 432, the terminate boot CMD0 command 432 maybe sent by the host 210 while the data lines are idle. In this example,the memory device will again exit boot mode upon the receipt 434 of theend bit of the valid terminate boot CMD0 command 432. Thus theembodiments of the present disclosure provide for a more robust methodof initiating and terminating a boot operation than previous methodsprovide. For example, a noise glitch appearing on the command line in asystem utilizing methods according to one or more embodiments of thepresent disclosure will not trigger a premature termination of the bootoperation because only a valid terminate boot command will cause thememory device to exit boot mode.

CONCLUSION

Memory devices and methods have been described capable of providing amore robust boot loading method. By utilizing a command indicative of adesire to initiate a boot operation and a command indicative of a desireto terminate the boot operation according to the one or more embodimentsof the present disclosure, a more reliable boot operation can berealized. The need for hardware modification to some hosts has also beeneliminated.

Although specific embodiments have been illustrated and describedherein, it will be appreciated by those of ordinary skill in the artthat any arrangement that is calculated to achieve the same purpose maybe substituted for the specific embodiments shown. Many adaptations ofthe disclosure will be apparent to those of ordinary skill in the art.Accordingly, this application is intended to cover any adaptations orvariations of the disclosure.

1. A method of operating a memory device, comprising: initiating a bootmode of operation of the memory device in response to receiving a firstcommand, wherein the first command comprises a pattern of two or morecommand signals; and terminating the boot mode of operation in responseto receiving a second command, wherein the second command comprises apattern of two or more command signals.
 2. The method of claim 1,further comprising outputting boot data from the memory device inresponse to receiving the first command
 3. The method of claim 2,wherein outputting boot data from the memory device further comprisesoutputting boot data stored in an area of the memory device designatedto store boot data.
 4. The method of claim 2, further comprisingoutputting a boot acknowledge signal from the memory device afterreceiving the first command and prior to outputting the boot data. 5.The method of claim 2, wherein terminating the boot mode of operationcomprises terminating the output of boot data from the memory device inresponse to receiving the second command.
 6. The method of claim 1,wherein a portion of the first command is different than a portion ofthe second command.
 7. The method of claim 1, wherein the first commandcomprises a particular command combined with a first argument and wherethe second command comprises the particular command combined with asecond argument different than the first argument.
 8. The method ofclaim 1, wherein the first command and the second command each conformto a CMD0 command of a Multimedia Card (MMC) memory device protocol. 9.A method of operating an electronic system having a controller coupledto a memory device, the method comprising: transmitting a first commandfrom the controller to the memory device indicative of a desire toinitiate a boot mode of operation of the memory device, wherein thefirst command comprises a pattern of two or more command signals; and ifit is desired to terminate the boot mode of operation, transmitting asecond command to the memory device, wherein the second commandcomprises a pattern of two or more command signals.
 10. The method ofclaim 9, further comprising initiating a boot mode of operation of thememory device in response to receiving the first command.
 11. The methodof claim 10, further comprising outputting boot data from the memorydevice to the controller after initiating the boot mode of operation ofthe memory device.
 12. The method of claim 11, further comprisingtransmitting a boot acknowledge signal from the memory device to thecontroller in response to receiving the first command and prior tooutputting boot data from the memory device.
 13. The method of claim 12,wherein transmitting a boot acknowledge signal further comprisestransmitting the boot acknowledge signal on a data line coupled betweenthe controller and the memory device.
 14. The method of claim 12,wherein transmitting a boot acknowledge signal further comprisestransmitting the boot acknowledge signal within a particular period oftime after receiving the first command.
 15. A method for operating anelectronic system having a controller coupled to a plurality of memorydevices, the method comprising: transmitting a first command from thecontroller to the plurality of memory devices indicative of a desire tooutput boot data stored in a particular memory device of the pluralityof memory devices, wherein the first command comprises a pattern of twoor more command signals; and if it is desired to terminate the output ofboot data, transmitting a second command to the plurality of memorydevices, wherein the second command comprises a pattern of two or morecommand signals.
 16. The method of claim 15, further comprising: whereinthe first command is a two-part command; wherein the second command is atwo-part command; wherein the first part of the first command is thesame as the first part of the second command; and wherein the secondpart of the first command is different than the second part of thesecond command
 17. The method of claim 15, wherein transmitting thefirst command from the controller to the plurality of memory devicesfurther comprises transmitting the first command to determine whichmemory device of the plurality of memory devices comprises theparticular memory device.
 18. The method of claim 15, further comprisingoutputting a boot acknowledge signal from the particular memory devicein response to the particular memory device receiving the first commandand prior to outputting the stored boot data.
 19. The method of claim15, further comprising terminating the output of the stored boot data inresponse to receiving the second command.
 20. The method of claim 19,wherein terminating the output of the stored boot data further comprisesterminating the output of the stored boot data prior to outputting allof the stored boot data only if the particular memory device receivesthe second command.